What needs to be configured?

The following outline gives you an idea of what needs to be done to configure the OPC Classic server and the OPC Classic client DCOM security. The instructions in the pages that follow in this section explain the details.

Outline for configuring the OPC Classic server (which could be CSense or a 3rd-party OPC Classic server)

  1. Configure a domain user and SQL user.

  2. Configure the firewall.

  3. Configure server-specific Component Services DCOM settings.

  4. Configure Component Services DCOM OPCEnum settings.
    This configuration makes the OPC Classic server visible to all OPC Classic clients querying which OPC Classic servers are available. This configuration is therefore not necessary if your company protocol does not allow remote OPC Classic clients to browse for all available OPC Classic servers.

No service changes are necessary on the server for DCOM.

Outline for configuring the OPC Classic client

  1. Configure a domain user, a SQL user, and services.

  2. Configure the firewall.

  3. Check client-specific Component Services DCOM settings. (Typically, no Component Services DCOM changes are necessary on the client.)

NOTE: To successfully configure the DCOM settings, you need to be logged in as an Administrator, or log in using an account with Administrative rights.

How do I make the changes take effect?

Configuration changes made

Required action
On either OPC Classic server or client: changes made to DCOM config or security settings. Restart the client or server application

Document your settings

A good practice is to document your DCOM configuration settings. Knowing how your machine was set up previously saves a lot of time when needing to reconfigure it after a possible hardware or drive failure or when someone else needs to do the configuration in future.


Related topics:

Configuring the OPC Classic server:

Configuring the OPC Classic client:

  

CSense 2023- Last updated: June 24,2025